-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: define QueryEngine
and wrap all things into it
#1160
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR looks very great! Lots of messy codes are deleted. I've left some comments for some trivial issues, and let's move on after they are resolved.
df1a5ee
to
3d66799
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
77098fb
to
1f31640
Compare
Rationale
When I add
PhysicalPlanEncoder
, I found there have been too many sub-modules inquery_engine
crate now... And I foudn in fact we always use them together, so I decide to defineQueryEngine
trait to integrate them.Detailed Changes
PhysicalPlanEncoder
and its datafusion impl.Executor
.QueryEngine
to integratePhysicalPlanner
,PhysicalPlanEncoder
,Executor
.Test Plan
Test by exist tests.